ci(deps): tighten OSV/dependency scan schedule from weekly to daily - #14934
Merged
Conversation
The scheduled scan (validate-deps.yml) is the discovery trigger for a new OSV advisory; the per-PR path trigger is the blocking trigger. Between weekly Monday runs, a new advisory could go undetected for up to six days, so the first PR touching a manifest ate a red unrelated to its diff — six occurrences in a month (#14645). Moves the cron from '0 3 * * 1' (weekly, Monday 03:00 UTC) to '0 3 * * *' (daily, same hour) — Option A from the card, ruled by the maintainer (issue comment #5523306978): tighten cadence now, defer the automatic issue-opening outlet (Option B) pending measurement of whether a daily red still goes unseen. The ruling names .github/workflows/osv-scanner.yml, which does not exist; applying its substance to validate-deps.yml, the file the card's own body correctly names and which actually carries this schedule trigger. Fixes #14645 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk
baozhoutao
added
the
skip-changeset
Claude
baozhoutao
marked this pull request as ready for review
September 3, 2026 11:24
baozhoutao
enabled auto-merge
September 3, 2026 11:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #14645
What
Moves the OSV/dependency scan's
scheduletrigger in.github/workflows/validate-deps.ymlfrom weekly (0 3 * * 1, Mondays) todaily (
0 3 * * *), keeping the same 03:00 UTC hour. This is Option A fromthe card's decision facets, ruled by the maintainer (issue comment
#5523306978):
tighten the discovery cadence; do not build an automatic issue-opening outlet
(Option B) in this change.
Filename correction
The ruling names
.github/workflows/osv-scanner.yml. That file does notexist on
main— the card's own body correctly names.github/workflows/validate-deps.yml(the file that actually carries theschedule:trigger,cron: '0 3 * * 1', andissues: write). This PRapplies the ruling's substance (weekly → daily, one cron line) to
validate-deps.yml, per the card's own correction note. The ruling itself isuntouched by this — only the filename it names was a clerical slip.
Scope
.github/workflows/validate-deps.ymlonly, as dispatched.skip-changeset: this PR publishes nothing from any released package.Clause-②: no.Validate Package Dependenciesis red for every PR touching a package.json — 4 FIXABLE OSV advisories in the lockfile (@xmldom/xmldom, qs) #14639's, separatelyqueued) and does not build Option B (no issue-opening step was added,
though the job already holds
issues: write).Findings (not actioned — reported per dispatch instructions)
validate-deps.ymlhas noconcurrency:guard. At a 24h cadence with ascan step that normally completes in minutes, back-to-back scheduled runs
overlapping is very unlikely, but it's an honest gap if a run ever hangs.
Reporting per the card's PM-assumption Implement ObjectStack protocol specification with Zod schemas and TypeScript interfaces #3 rather than expanding this diff.
Tests
See the report comment on #14645 for the full gate list and exit codes.
🤖 Generated with Claude Code
https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk
Generated by Claude Code